Creation and Management of RFID Device Versions

ABSTRACT

The claimed subject matter provides a system and/or method that creates, manages, or maintains multiple device versions in a network of Radio Frequency Identification (RFID) devices. The system can include components that detect whether a device has joined the network and based at least in part on such indication creates a device profile the first time that the device is detected, establishes a version trail containing configuration settings specific to the detected device, and thereafter builds and maintains the version trail when the device joins and/or leaves the network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is a continuation of co-pendingU.S. patent application Ser. No. 15/089,887 entitled “Creation andManagement of Device Versions” and filed Apr. 4, 2016 which is acontinuation of U.S. patent application Ser. No. 14/861,115 entitled“Creation and Management of RFID Device Versions” and filed Sep. 22,2015 which is a continuation of U.S. patent application Ser. No.11/845,532 entitled “Creation and Management of RFID Device Versions”and filed Aug. 27, 2007, which are incorporated herein by reference.

BACKGROUND

Many retail, manufacture, and distribution establishments are applyingdifferent and innovative methods to increase efficiency. Theseestablishments can monitor store inventory to facilitate optimizingsupply and demand relating to customers. One aspect of maximizing profitmargins hinges on properly stocking inventory such that replenishmentoccurs in conjunction with exhaustion of goods and/or products. Forinstance, a retailer selling computers and/or consumer electroniccomponents, such as VCRs, DVDs, and the like, typically must stock suchretail items in relation to its customer sales. Thus, if computers aresubject to higher demand than other consumer electronic components, thenthe retailer will need to replenish stock in computers more frequentlythan other consumer electronic items in order to optimize supply anddemand, and in turn, profit. Monitoring inventory and associated salescan typically be a daunting and complex task, wherein product activityis comparable to a black box since inner workings can be unfathomableand unknown; yet monitoring products can be a crucial element ininventory/product efficiency.

Automatic identification and data capture (AIDC) technologies, andspecifically, Radio Frequency Identification (RFID) has been developedbased at least in part on the perceived need to cure deficiencies oftypical monitoring systems and/or methodologies (e.g., barcode readers,barcodes, and/or Universal Product Codes (UPCs). Radio FrequencyIdentification (RFID) can be a technique that effectuates andfacilitates remotely storing and/or retrieving data through utilizationof Radio Frequency Identification (RFID) tags. Since Radio FrequencyIdentification (RFID) systems are generally based on radio frequency andassociated signals, numerous benefits and/or advantages over traditionaltechniques in monitoring products can be evident. Radio FrequencyIdentification (RFID) technologies generally do not require a line ofsight in order to monitor products and/or receive signals fromconfederated Radio Frequency Identification (RFID) tags. Consequently,no manual scan is necessary wherein a scanner is required to be in closeproximity of the target (e.g., product, item of interest, etc.).Nevertheless, range can be limited in Radio Frequency Identification(RFID) based on radio frequency employed, Radio Frequency Identification(RFID) tag size, and associated power source. Further, Radio FrequencyIdentification (RFID) systems can allow multiple reads within secondsproviding quick scans and identifications. Radio FrequencyIdentification (RFID) systems thus allows a plurality of tags to be readand/or identified when Radio Frequency Identification (RFID) tags arewith a range of an Radio Frequency Identification (RFID) device orreader. The capability of multiple reads in an Radio FrequencyIdentification (RFID) system can be complimented with the ability toprovide informational tags that can contain unique identification codesto each individual product.

Furthermore, Radio Frequency Identification (RFID) systems and/ormodalities can provide real-time data associated with Radio FrequencyIdentification (RFID) tagged items. Real-time data streams allowretailers, distributors, and/or manufacturers the ability to monitorinventory and/or products with exactitude and precision. Employing RadioFrequency Identification (RFID) can further effectuate and facilitatethe supply of products in both front-end distributions (e.g., retailersto customers) and back-end distributions (e.g.,distributors/manufacturers to retailers). Distributors/manufacturers canscrutinize and monitor shipments of goods, quality, quantity, shippingand transit times, etc. In addition, retailers can track quantities ofinventory received, location of such inventory, quality, shelf-life,etc. The aforementioned benefits demonstrate a few instances of theversatility and flexibility of Radio Frequency Identification (RFID)technologies to function across multiple domains, such as, front-endsupply, back-end supply, distribution chains, manufacturing, retail,automation, etc.

A Radio Frequency Identification (RFID) system can consist of RadioFrequency Identification (RFID) tags and Radio Frequency Identification(RFID) transceivers. Radio Frequency Identification (RFID) tags cancontain an antenna that provides reception and/or transmission of radiofrequency queries from Radio Frequency Identification (RFID)transceivers. Radio Frequency Identification (RFID) tags can typicallybe a small object, such as, for instance, adhesive stickers, flexiblelabels, integrated chips, and the like. Typically there are fourfrequencies Radio Frequency Identification (RFID) tags can utilize: lowfrequency (e.g., between about 125 to 134 kilohertz (KHz)), highfrequency (about 13.56 megahertz (MHz)), Ultra High Frequency (UHF)(about 868 to 956 megahertz (MHz)) and Microwave (about 2.45 gigahertz(GHz)).

In general, Radio Frequency Identification (RFID) systems can includemultiple components: tags, tag readers (e.g., tag transceivers), tagwriters, tag programming stations, circulation readers, sortingequipment, tag inventory wands, and the like. Further, various makes,models, and/or types can be associated with respective components (e.g.,tags, devices, Radio Frequency Identification (RFID) devices, tagreaders, tag programming stations, circulation readers, . . . ). Eachcomponent and/or device can over the life time of the device requireroutine software updates, temporary and/or permanent re-configuration,and/or manipulation in order to function properly within a dynamic andconstantly changing working environment. Thus, given the large number ofinterdependent configuration settings that deal with Radio FrequencyIdentification (RFID) devices, and more particularly, with the RadioFrequency (RF) aspects (e.g., network settings, antenna configuration,etc.) associated with such devices, and the complexity involved inconfiguring and managing such devices, enterprise administrators requiresystems and methods to manage and monitor such change in a comprehensiveand rational manner.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosed subject matter. Thissummary is not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

The subject matter as claimed relates to systems and methods thatfacilitate and effectuate creation and management of Radio FrequencyIdentification (RFID) device versions in a comprehensible, auditable,and simple manner. More particularly, the claimed subject matterprovides a thorough audit trail and history of changes that occur toindividual Radio Frequency Identification (RFID) devices (and individualcomponents thereof) incorporated or included in a network of RadioFrequency Identification (RFID) enable devices and non-Radio FrequencyIdentification (RFID) enabled-devices.

The claimed subject matter in accordance with one aspect can providedevice version schemas, check pointing of device versions at detectionor connect time, display (graphical and/or textual) of differencesbetween versions of a particular device, and application of prior deviceversions (or saved device versions) to a device.

To the accomplishment of the foregoing and related ends, certainillustrative aspects of the disclosed and claimed subject matter aredescribed herein in connection with the following description and theannexed drawings. These aspects are indicative, however, of but a few ofthe various ways in which the principles disclosed herein can beemployed and is intended to include all such aspects and theirequivalents. Other advantages and novel features will become apparentfrom the following detailed description when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a machine-implemented system that creates, manages,and/or maintains Radio Frequency Identification (RFID) device versionsin a radio frequency identification network in accordance with theclaimed subject matter.

FIG. 2 depicts machine-implemented system that creates, manages, and/ormaintains Radio Frequency Identification (RFID) device versions in aradio frequency identification network in accordance with one aspect ofthe claimed subject matter.

FIG. 3 provides a more detailed depiction of an illustrative managementcomponent that creates, manages, and/or maintains Radio FrequencyIdentification (RFID) device versions in a radio frequencyidentification network in accordance with an aspect of the claimedsubject matter.

FIG. 4 illustrates a system implemented on a machine that creates,manages, and/or maintains Radio Frequency Identification (RFID) deviceversions in a radio frequency identification network in accordance withan aspect of the claimed subject matter.

FIG. 5 provides a further depiction of a machine implemented system thatcreates, manages, and/or maintains Radio Frequency Identification (RFID)device versions in a radio frequency identification network inaccordance with an aspect of the subject matter as claimed.

FIG. 6 illustrates yet another aspect of the machine implemented systemthat creates, manages, and/or maintains Radio Frequency Identification(RFID) device versions in a radio frequency identification network inaccordance with an aspect of the claimed subject matter.

FIG. 7 depicts a further illustrative aspect of the machine implementedsystem that creates, manages, and/or maintains Radio FrequencyIdentification (RFID) device versions in a radio frequencyidentification network in accordance with an aspect of the claimedsubject matter.

FIG. 8 illustrates another illustrative aspect of a system implementedon a machine that creates, manages, and/or maintains Radio FrequencyIdentification (RFID) device versions in a radio frequencyidentification network in accordance of yet another aspect of theclaimed subject matter.

FIG. 9 depicts yet another illustrative aspect of a system that creates,manages, and/or maintains Radio Frequency Identification (RFID) deviceversions in a radio frequency identification network in accordance withan aspect of the subject matter as claimed.

FIG. 10 illustrates a flow diagram of a machine implemented methodologythat creates, manages, and/or maintains Radio Frequency Identification(RFID) device versions in a radio frequency identification network inaccordance with an aspect of the claimed subject matter.

FIG. 11 illustrates a block diagram of a computer operable to executethe disclosed system in accordance with an aspect of the claimed subjectmatter.

FIG. 12 illustrates a schematic block diagram of an exemplary computingenvironment for processing the disclosed architecture in accordance withanother aspect.

DETAILED DESCRIPTION

The subject matter as claimed is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding thereof. It may be evident, however, that theclaimed subject matter can be practiced without these specific details.In other instances, well-known structures and devices are shown in blockdiagram form in order to facilitate a description thereof.

Radio Frequency Identification (RFID) devices are typically extremelycomplex to maintain and manage. For instance, a typical Radio FrequencyIdentification (RFID) device can consist of many hundreds, if notthousands, of interdependent configuration settings that can deal withRadio Frequency (RF) parameters, network settings, and/or antennaconfiguration aspects of the device. Consequently, an enterpriseadministrator, during the course of administering Radio FrequencyIdentification (RFID) devices, can make many multiple changes to theconfiguration of a particular Radio Frequency Identification (RFID)device. For example, during the course of time (e.g., during the courseof a week) an administrator can configure and re-configure, as the needarises, a particular Radio Frequency Identification (RFID) transceiverdevice (e.g., a Radio Frequency Identification (RFID) tag reader) foruse at a North Receiving Dock Door on Monday, a South Dispatching DockDoor on Wednesday, as a field enabled device on Thursday morning, andback to a North Receiving Dock Door on Friday afternoon. In order tofacilitate and effectuate such fluidity the claimed subject matter can,for example, employ a versioning schema, check point a device at connector detect time, display graphically and/or textually differences betweendevice versions, and apply saved or persisted device versions (orselected properties thereof) to identified devices.

FIG. 1 depicts an illustrative system 100 that creates, manages and/ormaintains Radio Frequency Identification (RFID) device versions in aradio frequency identification network in accordance with an aspect ofthe claimed subject matter. System 100 can comprise server 102 that caninclude the functionality of database management services. Such databasefunctionality as employed by server 102 can include utilization ofmodeling languages to define schema based on one or more databasemanagement organizational (e.g., hierarchical, network, relationaland/or object, etc.) model, data structures (e.g., fields, records,files, and/or objects) optimized to deal with large amounts of datapersisted on storage devices (both local and remote), and/or querylanguages and report writers that permit users and administrators tointeractively interrogate the database, analyze the data containedtherein, and create, modify, and/or update data according to pre-set ordynamically or contemporaneously determined privileges. Additionally,database functionality utilized by server 102 can include transactionmechanisms that can typically guarantee ACID (Atomicity, Consistency,Isolation, Durability) properties in order to ensure data integrity inthe face of concurrent user access (e.g., concurrency control) and theperiodic emergence of faults or errors (e.g., fault tolerance).

Additionally and/or alternatively, server 102 can be implementedentirely in software, hardware, and/or a combination of software and/orhardware. Further, server 102 can be incorporated within and/orassociated with other compatible components, such as for instance,devices and/or appliances that can include processors (e.g., desktopcomputers, laptop computers, notebook computers, cell phones, smartphones, Personal Digital Assistants (PDAs), multimedia Internet enabledmobile phones, multimedia players, and the like). As depicted, server102 can be in continuous and operative, or sporadic and intermittentcommunication via network topology 104 with device_(A) 106 ₁-device_(B)106 _(Q) (hereinafter collectively referred to as “devices 106”), whereA, B, and Q denote integers greater than or equal to zero (0).

Network topology 104 can include any viable communication and/orbroadcast technology, for example, wired and/or wireless modalitiesand/or technologies can be utilized to effectuate the claimed subjectmatter. Moreover, network topology 104 can include utilization ofPersonal Area Networks (PANs), Local Area Networks (LANs), Campus AreaNetworks (CAMs), Metropolitan Area Networks (MANs), extranets,intranets, the Internet, Wide Area Networks (WANs)—both centralized anddistributed—and/or any combination, permutation, and/or aggregationthereof.

Devices 106 can be any type of machine that includes a processor andcapable of effective communication with network topology 104. Machinesand/or services that can comprise devices 106 can include desktopcomputers, server class computing devices, cell phones, smart phones,laptop computers, notebook computers, Tablet PCs, consumer and/orindustrial devices and/or appliances, hand-held appliances and/ordevices, Personal Digital Assistants (PDAs), multimedia Internet mobilephones, printers, readers, transmitters, sensors, real-time devicesand/or sensors, devices extensible to a web service, real-time eventgeneration systems, and the like. Additionally, devices 106 can includeRadio Frequency Identification (RFID) specific devices, such as readers,sensors, writers, printers, tag programming stations, circulationreaders, sorting equipment, tag inventory wands, etc. As will beappreciated by those conversant in the art, devices 106 can include anycombination and/or permutation of the foregoing devices 106 withoutprejudice, limitation, or disclaimer. Additionally, as will be furtherappreciated by those cognizant of the art, network topology 104 caninclude any and all combinations and/or permutation of the foregoingdevices 106 with departing from the spirit, intent, and/or ambit of theclaimed subject matter.

In addition, devices 106 can include antennae 108 ₁, 108 ₂, . . . , 108_(W), where W represents a positive integer, whole number, or naturalnumber greater than or equal zero (0). Unless otherwise indicated,antennae 108 ₁, 108 ₂, . . . , 108 _(W), hereinafter can collectively bereferred to as “antenna 108”. As illustrated in FIG. 1, device_(A) 106 ₁has two antennae 108 ₁ and 108 ₂ associated therewith whereas device_(B)can have confederated a single antenna 108 _(W). Antennae 108 ₁, 108 ₂,. . . , 108 _(W) can include utilization of balanced and/or unbalancedantenna technologies. Moreover, devices 106 can be associated with, andcan have control over, more than one antenna 108

FIG. 2 provides a more detailed depiction 200 of server 102 thatcreates, manages and/or maintains Radio Frequency Identification (RFID)device versions in accordance with an illustrative aspect of the claimedsubject matter. Server 102 as depicted can include interface component202 (hereinafter referred to as “interface 202”) that can be incontinuous and/or intermittent communication with devices 106 vianetwork topology 104. Additionally, server 102 can also includemanagement component 204 that can, for instance, continuously and/orsporadically poll, interrogate, examine and/or enumerate the quantity,type, and configuration parameters of devices 106 extant on, or that canform, network topology 104, as well as detect and configure devicesnewly added (e.g., devices for which server 102 has no prior record) tonetwork topology 104. Management component 204 can thereafter persistsuch received, elicited, obtained, and/or derived information to localand/or remotely situated primary and/or secondary storage media asversions or time synchronized instances of current configurationparameters or settings of devices 106 at any instant in time. Suchversioning information can be employed to configure, customize, and/orreset currently non-functioning or dysfunction devices 106 (e.g., RadioFrequency Identification (RFID) devices) to settings that can have beenoptimal in the past. Additionally and/or alternatively versioning datacontemporaneously and/or previously developed, established, or deducedby management component 204 can be utilized to configure or re-configureostensibly functional devices 106 to other forms of device. Forinstance, a fully functioning portable Radio Frequency Identification(RFID) wand tag reader employed in an enterprise factory environment canbe temporarily configured for use in the field (e.g., at asub-contractors work-shop) and thereafter can be reconfigured back tothose configuration settings that existed immediately prior to itsexcursion into the field.

Interface 202 can receive data from a multitude of sources, such as, forexample, those associated with a particular individual Radio FrequencyIdentification (RFID) device (or components parts of the Radio FrequencyIdentification (RFID) device), client applications, services, users,clients, and/or entities involved with a particular transaction, aportion of transaction, and thereafter convey the received informationto management component 204 for further analysis and/or evaluation.Additionally, interface 202 can receive data from management component204 which then can be utilized to present (e.g., through a graphical ortextual display modality) configuration alternatives based on persisted,or contemporaneously derived, versioning information associated withdevices 106, or device classifications (e.g., certain selectconfiguration parameters employed by Radio Frequency Identification(RFID) tag readers can be similar or common to all such tag readers).

Interface 202 can provide various adapters, connectors, channels,communication pathways, etc. to integrate the various componentsincluded in system 200 into virtually any operating system and/ordatabase system and/or with one another. Additionally, interface 202 canprovide various adapters, connectors, channels, communicationmodalities, etc. that provide for interaction with various componentsthat can comprise system 200, and/or any other component (externaland/or internal), data and the like associated with system 200.

Management component 204 can keep track of all changes that occur toparticular devices 106 (and component parts thereof) over time and canfurther aggregate changes that ensue in the interim between set pointsor check points (e.g., two or more instance in time) as versions.Accordingly, whenever a Radio Frequency Identification (RFID) deviceconfiguration changes management component 204 can capture the changesand persist the change as part of a device setting associated with aparticular Radio Frequency Identification (RFID) device or class ofRadio Frequency Identification (RFID) device. Such functionality allowsmanagement component 204 and/or an administrator (e.g., situated in CapeCoral, Fla.) of an enterprise system (e.g., located in Iqaluit, Nunavut,Canada) to ascertain when a particular device, class of devices, set ofdisparate devices located in specific locations in the enterprise (e.g.,Radio Frequency Identification (RFID) devices at the East Receiving Doorof the factory located in Antananarivo, Madagascar), and/or variousclasses of similar and/or select devices situated and dispersedthroughout the extent of the enterprise become non-functional, and todetermine the rationale for the discontinuance by employing an audittrail that can be dynamically and/or contemporaneously constructed bymanagement component 204. The audit trail established by managementcomponent 204 can include information about what changes were madebetween set points or check points (e.g., today, yesterday, day beforeyesterday, etc.), who made the changes, why the changes were made, howthe changes were made, and when the changes were made, and furtherallows administrators to view differences or deltas (e.g., incrementalor marginal changes) from a current (e.g., possibly non-functional)parametric arrangement to a previous (e.g., ostensibly functional)device configuration. In this manner management component 204 and/or anadministrator employing the subject matter as claimed can obtaininformation as to device versioning as well as information regardingspecific and/or generic device implementation and/or configuration.

Further management component 204 can employ a device version schema thatcaptures device version changes into a database (e.g., Radio FrequencyIdentification (RFID) Store database). The database based at least inpart on the device version schema can thus establish, construct, orutilize device version tables, for example, that can persist theprogression of changes that can ensue during the existence of each andevery one devices 106 (or component parts thereof) in network topology104. It should be noted that while the claimed subject matter isexposited in terms of database tables those skilled in the art willappreciate that other salient and suitable structures (e.g., linkedlists, binary and/or multi-way trees, hashes, queues, stacks, etc.) canbe employed without departing from the spirit, scope, or intent of thesubject matter as claimed. Accordingly, when a connection is initiallyestablished to devices 106, management component 204 can create,assemble, or construct a property profile that can describe a set ofproperties that can be configuration settings associated with each ofdevices 106. The property profile can be stored on local and/or remotepersistence devices such as volatile memory or non-volatile memory, orboth volatile and non-volatile memory. For example, if a Radio FrequencyIdentification (RFID) reader is introduced to network topology 104,management component 204 via interface 202 can cause the newly addeddevice to divulge, or alternatively and/or additionally, obtain orconstruct/build a property profile for the added device. Once a propertyprofile has been constructed, built, or elicited it can be stored in thedatabase (e.g., Radio Frequency Identification (RFID) Store database).It should be noted that the property profile elicited, built, orconstructed can be distinct or separate from the device version tablesthat persist the progression of changes that can ensue during theexistence of devices 106 within network topology 104.

As can be appreciated there are many operations that can be undertakenthat can produce parametric changes to Radio Frequency Identification(RFID) devices. For instance, adding devices to network topology 104 cancreate a first version, changing properties (e.g., changing the name,location, or functionality of the device) can create a further version;any agent of change or modification, no matter how trivial, can generatedisparate synchronized instances or versions.

Turning now to FIG. 3 depicted therein is a more detailed illustration300 of management component 204 in accordance with an aspect of theclaimed subject matter. As illustrated management component 204 caninclude addition component 302 that can detect when a connection isinitially established with a device, and more particularly, with a RadioFrequency Identification device. Addition component 302 can upondetection of the device probe the device to relinquish or supplypertinent data about itself (e.g., Media Access Control (MAC) address,device type, hardware serial number, etc.). With such information,addition component 302 can create, assemble, or establish a propertyprofile that adequately distinguishes, differentiates, and/or describesa set of properties or configuration settings associated with thedetected device. On completion, or during the course of construction,addition component 302 can store the established property profile tostorage media associated with server 102, for example. Additionallyaddition component 302 can cause a database entry to be made inpre-established device version table, or where no device version tablehas previously been created; addition component 302 can create thedevice version table and subsequently populate the table withappropriate entries and/or parameters pertaining to detected devices.

Management component 204 can further include change component 304 thatcan allow management component 204 (or components thereof) oradministrators, for example, through textual or graphical interfaces, toeffectuate the administration, modification or change of existing deviceparameters. For example, change component 304 can permit anadministrator to change antenna parameters associated with a particularRadio Frequency Identification (RFID) device. As further illustrationchange component 304 can be employed by management component 204 (orselected components thereof) to modify network settings, or effectuatename changes to associated devices. As will be appreciated each of thesechange activities can initiate the creation of a new instance or versionof the associated device characteristics.

Additionally, management component 204 can include application component306 that allows management component 204 via interface 202, oralternatively and/or additionally, an administrator employing graphicaland/or textual interfaces to modify device settings to prior or previousversions or instances associated with a particular device. Further,application component 306 can customize selected configuration settingsassociated with a device to prior or previous version instances of thatparticular device and/or particular device class. For example,application component 306 can based at least in part on device typeselectively customize configuration parameters for an entire class ofRadio Frequency Identification (RFID) wand tag readers. As a furtherexample application component 306 can discriminately apply devicesettings on particular and/or selected devices, where each of the devicesettings emanates from one or more previously established versionsassociated with the selected devices or from a device class to which theselected device belong.

Management component 204 can also include view component 308 that can beused in conjunction with management component 204, and/or by anenterprise administrator to present device configuration and versioninformation in an easily understandable or comprehensible categorizedmanner. View component 308 can utilize versioning information (e.g.,versions persisted in device version tables, configuration information,and the like) can be extracted, selected, deduced, or derived andthereafter displayed or presented in a familiar easy to use categorizedfashion for use by an administrator.

Moreover, management component 204 can include difference engine 310that can produce and located differences between two more versions. Sucha facility can aid in identifying where problems have arisen in thepast, and might arise in the future. Administrators can be utilizeddifference engine 310 to view cumulative and/or iterative differences.For example, difference engine 310 can be employed to find distinctionsbetween version 1 and version X of a particular device. Differenceslocated by difference engine 310 can be display in an textual and/orgraphical manner. For instance, differences can be color coded,highlighted, or only fields that are different displayed, inside-by-side comparison between two versions.

Further, management component 204 can include check point component 312that creates a version based at least in part on the current propertiesof the device by connecting to the device to retrieve or elicit settingsand/or configuration parameters. Such a feature can be useful when adevice changed out of the Radio Frequency Identification (RFID) platform(e.g., used for some other functionality not typically related to RadioFrequency Identification (RFID) capabilities). For example, if a deviceis configured outside the ambit of the claimed subject matter, when thedevice is introduced into, or re-introduced back into, the RadioFrequency Identification (RFID) network, the device may be renderednon-functional. The check point component 312 allows the claimed subjectmatter to take into account that settings may have been changeexternally (not just through the claimed subject matter) and that suchsetting can be functionally valid externally, though such setting areinoperative in the internal (e.g., the Radio Frequency Identification(RFID)) network. Thus, the check pointing feature provided by checkpoint component 312 obtains or retrieves any changes that may havetranspired back to the version table whether or not the detected changeled to a functionally but valid, functionally but invalid,non-functionally but valid, or non-functionally but invalidconfiguration.

Furthermore, management component 204 can additionally include discoveryengine 314 that effectuates and facilitate device discovery whenever adevice is added or returns to the Radio Frequency Identification (RFID)network. Discovery engine 314 on detection of a device immediately anddynamically captures settings resident on the detected device andpersists these settings into a store and thereafter makes these settingsavailable for the administrator if the need arises to commenceconfiguring the detected device appropriately for use with the claimedsubject matter. For example, a mobile device can periodically and/orpermanently enter and/or exit from the purview of the claimed subjectmatter. During the transition period—a user of the mobile device canhave configured the settings on the device—so when the device returnsback to the enterprise and is once again re-introduce into theestablished Radio Frequency Identification (RFID) network, a discoveryor discovery update can be automatically undertaken. It should be notedthat as part of the discovery process an administrator can indicate thatwhen a particular device returns to the Radio Frequency Identification(RFID) network that properties associated with the detected and/orreturned device should be set to a particular version associated withthe device prior to its exit from the established network. Alternative,the administrator can indicate that when a device returns that new ornovel setting (e.g., due to a software upgrade or patch release, etc.)or profile.

In addition, management component 204 can also include audit component316 that provides an auditing trail keyed to each device included in theRadio Frequency Identification (RFID) network. Such an audit trail asmaintained by audit component 316 can provide information as to why achange was made, what necessitated the change, how the change was made,who made the change, when the change was made, and which parameters weremodified during the change. Such information can be extremely useful introuble shooting dysfunctional device configurations.

FIG. 4 depicts an aspect of a system 400 that creates, manages and/ormaintains Radio Frequency Identification (RFID) device versions in aradio frequency identification network. System 400 can include store 402that can include any suitable data necessary for management component204 to facilitate it aims. For instance, store 402 can includeinformation regarding user data, data related to a portion of atransaction, credit information, historic data related to a previoustransaction, a portion of data associated with purchasing a good and/orservice, a portion of data associated with selling a good and/orservice, geographical location, online activity, previous onlinetransactions, activity across disparate network, activity across anetwork, credit card verification, membership, duration of membership,communication associated with a network, buddy lists, contacts,questions answered, questions posted, response time for questions, blogdata, blog entries, endorsements, items bought, items sold, products onthe network, information gleaned from a disparate website, informationgleaned from the disparate network, ratings from a website, a creditscore, geographical location, a donation to charity, or any otherinformation related to software, applications, web conferencing, and/orany suitable data related to transactions, etc.

It is to be appreciated that store 402 can be, for example, volatilememory or non-volatile memory, or can include both volatile andnon-volatile memory. By way of illustration, and not limitation,non-volatile memory can include read-only memory (ROM), programmableread only memory (PROM), electrically programmable read only memory(EPROM), electrically erasable programmable read only memory (EEPROM),or flash memory. Volatile memory can include random access memory (RAM),which can act as external cache memory. By way of illustration ratherthan limitation, RAM is available in many forms such as static RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM),Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM) and Rambusdynamic RAM (RDRAM). Store 402 of the subject systems and methods isintended to comprise, without being limited to, these and any othersuitable types of memory. In addition, it is to be appreciated thatstore 402 can be a server, a database, a hard drive, and the like.

FIG. 5 provides yet a further depiction of a system 500 that creates,manages and/or maintains Radio Frequency Identification (RFID) deviceversions in a radio frequency identification network in accordance withan aspect of the claimed subject matter. As depicted, system 500 caninclude a data fusion component 502 that can be utilized to takeadvantage of information fission which may be inherent to a process(e.g., receiving and/or deciphering inputs) relating to analyzing inputsthrough several different sensing modalities. In particular, one or moreavailable inputs may provide a unique window into a physical environment(e.g., an entity inputting instructions) through several differentsensing or input modalities. Because complete details of the phenomenato be observed or analyzed may not be contained within a singlesensing/input window, there can be information fragmentation whichresults from this fission process. These information fragmentsassociated with the various sensing devices may include both independentand dependent components.

The independent components may be used to further fill out (or span) aninformation space; and the dependent components may be employed incombination to improve quality of common information recognizing thatall sensor/input data may be subject to error, and/or noise. In thiscontext, data fusion techniques employed by data fusion component 502may include algorithmic processing of sensor/input data to compensatefor inherent fragmentation of information because particular phenomenamay not be observed directly using a single sensing/input modality.Thus, data fusion provides a suitable framework to facilitatecondensing, combining, evaluating, and/or interpreting available sensedor received information in the context of a particular application.

FIG. 6 provides a further depiction of a system 600 that creates,manages and/or maintains Radio Frequency Identification (RFID) deviceversions in a radio frequency identification network in accordance withan aspect of the claimed subject matter. As illustrated managementcomponent 204 can, for example, employ synthesizing component 602 tocombine, or filter information received from a variety of inputs (e.g.,text, speech, gaze, environment, audio, images, gestures, noise,temperature, touch, smell, handwriting, pen strokes, analog signals,digital signals, vibration, motion, altitude, location, GPS, wireless,etc.), in raw or parsed (e.g. processed) form. Synthesizing component602 through combining and filtering can provide a set of informationthat can be more informative, or accurate (e.g., with respect to anentity's communicative or informational goals) and information from justone or two modalities, for example. As discussed in connection with FIG.5, the data fusion component 502 can be employed to learn correlationsbetween different data types, and the synthesizing component 602 canemploy such correlations in connection with combining, or filtering theinput data.

FIG. 7 provides a further illustration of a system 700 that can creates,manages and/or maintains Radio Frequency Identification (RFID) deviceversions in a radio frequency identification network in accordance withan aspect of the claimed subject matter. As illustrated managementcomponent 204 can, for example, employ context component 702 todetermine context associated with a particular action or set of inputdata. As can be appreciated, context can play an important role withrespect understanding meaning associated with particular sets of input,or intent of an individual or entity. For example, many words or sets ofwords can have double meanings (e.g., double entendre), and withoutproper context of use or intent of the words the corresponding meaningcan be unclear thus leading to increased probability of error inconnection with interpretation or translation thereof. The contextcomponent 702 can provide current or historical data in connection withinputs to increase proper interpretation of inputs. For example, time ofday may be helpful to understanding an input—in the morning, the word“drink” would likely have a high a probability of being associated withcoffee, tea, or juice as compared to be associated with a soft drink oralcoholic beverage during late hours. Context can also assist ininterpreting uttered words that sound the same (e.g., steak and, andstake). Knowledge that it is near dinnertime of the user as compared tothe user campaign would greatly help in recognizing the following spokenwords “I need a steak/stake”. Thus, if the context component 702 hadknowledge that the user was not camping, and that it was neardinnertime, the utterance would be interpreted as “steak”. On the otherhand, if the context component 702 knew (e.g., via GPS system input)that the user recently arrived at a camping ground within a nationalpark; it might more heavily weight the utterance as “stake”.

In view of the foregoing, it is readily apparent that utilization of thecontext component 702 to consider and analyze extrinsic information cansubstantially facilitate determining meaning of sets of inputs.

FIG. 8 a further illustration of a system 800 that creates, managesand/or maintains Radio Frequency Identification (RFID) device versionsin a radio frequency identification network in accordance with an aspectof the claimed subject matter. As illustrated, system 800 can includepresentation component 802 that can provide various types of userinterface to facilitate interaction between a user and any componentcoupled to management component 204. As illustrated, presentationcomponent 802 is a separate entity that can be utilized with managementcomponent 204. However, it is to be appreciated that presentationcomponent 802 and/or other similar view components can be incorporatedinto management component 204 and/or a standalone unit. Presentationcomponent 802 can provide one or more graphical user interface, commandline interface, and the like. For example, the graphical user interfacecan be rendered that provides the user with a region or means to load,import, read, etc., data, and can include a region to present theresults of such. These regions can comprise known text and/or graphicregions comprising dialog boxes, static controls, drop-down menus, listboxes, pop-up menus, edit controls, combo boxes, radio buttons, checkboxes, push buttons, and graphic boxes. In addition, utilities tofacilitate the presentation such as vertical and/or horizontalscrollbars for navigation and toolbar buttons to determine whether aregion will be viewable can be employed. For example, the user caninteract with one or more of the components coupled and/or incorporatedinto management component 204.

Users can also interact with regions to select and provide informationvia various devices such as a mouse, roller ball, keypad, keyboard,and/or voice activation, for example. Typically, the mechanism such as apush button or the enter key on the keyboard can be employed subsequentto entering the information in order to initiate, for example, a query.However, it is to be appreciated that the claimed subject matter is notso limited. For example, nearly highlighting a checkbox can initiateinformation conveyance. In another example, a command line interface canbe employed. For example, the command line interface can prompt (e.g.,via text message on a display and an audio tone) the user forinformation via a text message. The user can then provide suitableinformation, such as alphanumeric input corresponding to an optionprovided in the interface prompt or an answer to a question posed in theprompt. It is to be appreciated that the command line interface can beemployed in connection with a graphical user interface and/orapplication programming interface (API). In addition, the command lineinterface can be employed in connection with hardware (e.g., videocards) and/or displays (e.g., black-and-white, and EGA) with limitedgraphic support, and/or low bandwidth communication channels.

FIG. 9 depicts a system 900 that employs artificial intelligence tocreate, manage, and/or maintain Radio Frequency Identification (RFID)device versions in a radio frequency identification network inaccordance with an aspect of the subject matter as claimed. Accordingly,as illustrated, system 900 can include an intelligence component 902that can employ a probabilistic based or statistical based approach, forexample, in connection with making determinations or inferences.Inferences can be based in part upon explicit training of classifiers(not shown) before employing system 200, or implicit training based atleast in part upon system feedback and/or users previous actions,commands, instructions, and the like during use of the system.Intelligence component 902 can employ any suitable scheme (e.g., numeralnetworks, expert systems, Bayesian belief networks, support vectormachines (SVMs), Hidden Markov Models (HMMs), fuzzy logic, data fusion,etc.) in accordance with implementing various automated aspectsdescribed herein. Intelligence component 902 can factor historical data,extrinsic data, context, data content, state of the user, and cancompute cost of making an incorrect determination or inference versusbenefit of making a correct determination or inference. Accordingly, autility-based analysis can be employed with providing such informationto other components or taking automated action. Ranking and confidencemeasures can also be calculated and employed in connection with suchanalysis.

In view of the exemplary systems shown and described supra,methodologies that may be implemented in accordance with the disclosedsubject matter will be better appreciated with reference to the flowchart of FIG. 10. While for purposes of simplicity of explanation, themethodologies are shown and described as a series of blocks, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methodologies described hereinafter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers.

The claimed subject matter can be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more components. Generally, program modules can include routines,programs, objects, data structures, etc. that perform particular tasksor implement particular abstract data types. Typically the functionalityof the program modules may be combined and/or distributed as desired invarious aspects.

FIG. 10 provides an illustrative flow diagram illustrating a method 1000that creates, manages, and/or maintains Radio Frequency Identification(RFID) device versions in a radio frequency identification network inaccordance with an aspect of the claimed subject matter. The methodcommences at 1002 where various and sundry initializations can takeplace after which the method can proceed to 1004. At 1004 the method candetect the presence, addition, and/or removal of Radio FrequencyIdentification (RFID) network. Where a device is detected as being addedor returning to the network, the method can either create a deviceprofile for the device, or update a previously persisted device profileat 1006. At 1008 the method can perform a check point function witheffectively creates a further version instance associated with thedetected device. Once a new version has been created at 1008 the methodcan return to 1004 to detect the presence of further additions and/orremovals of devices to the Radio Frequency Identification (RFID)network.

The claimed subject matter can be implemented via object orientedprogramming techniques. For example, each component of the system can bean object in a software routine or a component within an object. Objectoriented programming shifts the emphasis of software development awayfrom function decomposition and towards the recognition of units ofsoftware called “objects” which encapsulate both data and functions.Object Oriented Programming (OOP) objects are software entitiescomprising data structures and operations on data. Together, theseelements enable objects to model virtually any real-world entity interms of its characteristics, represented by its data elements, and itsbehavior represented by its data manipulation functions. In this way,objects can model concrete things like people and computers, and theycan model abstract concepts like numbers or geometrical concepts.

The benefit of object technology arises out of three basic principles:encapsulation, polymorphism and inheritance. Objects hide or encapsulatethe internal structure of their data and the algorithms by which theirfunctions work. Instead of exposing these implementation details,objects present interfaces that represent their abstractions cleanlywith no extraneous information. Polymorphism takes encapsulationone-step further—the idea being many shapes, one interface. A softwarecomponent can make a request of another component without knowingexactly what that component is. The component that receives the requestinterprets it and figures out according to its variables and data how toexecute the request. The third principle is inheritance, which allowsdevelopers to reuse pre-existing design and code. This capability allowsdevelopers to avoid creating software from scratch. Rather, throughinheritance, developers derive subclasses that inherit behaviors thatthe developer then customizes to meet particular needs.

In particular, an object includes, and is characterized by, a set ofdata (e.g., attributes) and a set of operations (e.g., methods), thatcan operate on the data. Generally, an object's data is ideally changedonly through the operation of the object's methods. Methods in an objectare invoked by passing a message to the object (e.g., message passing).The message specifies a method name and an argument list. When theobject receives the message, code associated with the named method isexecuted with the formal parameters of the method bound to thecorresponding values in the argument list. Methods and message passingin OOP are analogous to procedures and procedure calls inprocedure-oriented software environments.

However, while procedures operate to modify and return passedparameters, methods operate to modify the internal state of theassociated objects (by modifying the data contained therein). Thecombination of data and methods in objects is called encapsulation.Encapsulation provides for the state of an object to only be changed bywell-defined methods associated with the object. When the behavior of anobject is confined to such well-defined locations and interfaces,changes (e.g., code modifications) in the object will have minimalimpact on the other objects and elements in the system.

Each object is an instance of some class. A class includes a set of dataattributes plus a set of allowable operations (e.g., methods) on thedata attributes. As mentioned above, OOP supports inheritance—a class(called a subclass) may be derived from another class (called a baseclass, parent class, etc.), where the subclass inherits the dataattributes and methods of the base class. The subclass may specializethe base class by adding code which overrides the data and/or methods ofthe base class, or which adds new data attributes and methods. Thus,inheritance represents a mechanism by which abstractions are madeincreasingly concrete as subclasses are created for greater levels ofspecialization.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component can be, but is not limited to being,a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers.

Artificial intelligence based systems (e.g., explicitly and/orimplicitly trained classifiers) can be employed in connection withperforming inference and/or probabilistic determinations and/orstatistical-based determinations as in accordance with one or moreaspects of the claimed subject matter as described hereinafter. As usedherein, the term “inference,” “infer” or variations in form thereofrefers generally to the process of reasoning about or inferring statesof the system, environment, and/or user from a set of observations ascaptured via events and/or data. Inference can be employed to identify aspecific context or action, or can generate a probability distributionover states, for example. The inference can be probabilistic—that is,the computation of a probability distribution over states of interestbased on a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines . . . ) canbe employed in connection with performing automatic and/or inferredaction in connection with the claimed subject matter.

Furthermore, all or portions of the claimed subject matter may beimplemented as a system, method, apparatus, or article of manufactureusing standard programming and/or engineering techniques to producesoftware, firmware, hardware or any combination thereof to control acomputer to implement the disclosed subject matter. The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device or media. For example,computer readable media can include but are not limited to magneticstorage devices (e.g., hard disk, floppy disk, magnetic strips . . . ),optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . .. ), smart cards, and flash memory devices (e.g., card, stick, key drive. . . ). Additionally it should be appreciated that a carrier wave canbe employed to carry computer-readable electronic data such as thoseused in transmitting and receiving electronic mail or in accessing anetwork such as the Internet or a local area network (LAN). Of course,those skilled in the art will recognize many modifications may be madeto this configuration without departing from the scope or spirit of theclaimed subject matter.

Some portions of the detailed description have been presented in termsof algorithms and/or symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions and/orrepresentations are the means employed by those cognizant in the art tomost effectively convey the substance of their work to others equallyskilled. An algorithm is here, generally, conceived to be aself-consistent sequence of acts leading to a desired result. The actsare those requiring physical manipulations of physical quantities.Typically, though not necessarily, these quantities take the form ofelectrical and/or magnetic signals capable of being stored, transferred,combined, compared, and/or otherwise manipulated.

It has proven convenient at times, principally for reasons of commonusage, to refer to these signals as bits, values, elements, symbols,characters, terms, numbers, or the like. It should be borne in mind,however, that all of these and similar terms are to be associated withthe appropriate physical quantities and are merely convenient labelsapplied to these quantities. Unless specifically stated otherwise asapparent from the foregoing discussion, it is appreciated thatthroughout the disclosed subject matter, discussions utilizing termssuch as processing, computing, calculating, determining, and/ordisplaying, and the like, refer to the action and processes of computersystems, and/or similar consumer and/or industrial electronic devicesand/or machines, that manipulate and/or transform data represented asphysical (electrical and/or electronic) quantities within the computer'sand/or machine's registers and memories into other data similarlyrepresented as physical quantities within the machine and/or computersystem memories or registers or other such information storage,transmission and/or display devices.

Referring now to FIG. 11, there is illustrated a block diagram of acomputer operable to execute the disclosed system. In order to provideadditional context for various aspects thereof, FIG. 11 and thefollowing discussion are intended to provide a brief, generaldescription of a suitable computing environment 1100 in which thevarious aspects of the claimed subject matter can be implemented. Whilethe description above is in the general context of computer-executableinstructions that may run on one or more computers, those skilled in theart will recognize that the subject matter as claimed also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the claimed subject matter may also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and non-volatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes both volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalvideo disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

With reference again to FIG. 11, the exemplary environment 1100 forimplementing various aspects includes a computer 1102, the computer 1102including a processing unit 1104, a system memory 1106 and a system bus1108. The system bus 1108 couples system components including, but notlimited to, the system memory 1106 to the processing unit 1104. Theprocessing unit 1104 can be any of various commercially availableprocessors. Dual microprocessors and other multi-processor architecturesmay also be employed as the processing unit 1104.

The system bus 1108 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1106includes read-only memory (ROM) 1110 and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatilememory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1102, such as during start-up. The RAM 1112 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1102 further includes an internal hard disk drive (HDD)1114 (e.g., EIDE, SATA), which internal hard disk drive 1114 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1116, (e.g., to read from or write to aremovable diskette 1118) and an optical disk drive 1120, (e.g., readinga CD-ROM disk 1122 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1114, magnetic diskdrive 1116 and optical disk drive 1120 can be connected to the systembus 1108 by a hard disk drive interface 1124, a magnetic disk driveinterface 1126 and an optical drive interface 1128, respectively. Theinterface 1124 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1194 interfacetechnologies. Other external drive connection technologies are withincontemplation of the claimed subject matter.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1102, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed and claimedsubject matter.

A number of program modules can be stored in the drives and RAM 1112,including an operating system 1130, one or more application programs1132, other program modules 1134 and program data 1136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1112. It is to be appreciated that the claimed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 1102 throughone or more wired/wireless input devices, e.g., a keyboard 1138 and apointing device, such as a mouse 1140. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1104 through an input deviceinterface 1142 that is coupled to the system bus 1108, but can beconnected by other interfaces, such as a parallel port, an IEEE 1194serial port, a game port, a USB port, an IR interface, etc.

A monitor 1144 or other type of display device is also connected to thesystem bus 1108 via an interface, such as a video adapter 1146. Inaddition to the monitor 1144, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1102 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1148. The remotecomputer(s) 1148 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1102, although, for purposes of brevity, only a memory/storage device1150 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1152 and/orlarger networks, e.g., a wide area network (WAN) 1154. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich may connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1102 isconnected to the local network 1152 through a wired and/or wirelesscommunication network interface or adapter 1156. The adaptor 1156 mayfacilitate wired or wireless communication to the LAN 1152, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adaptor 1156.

When used in a WAN networking environment, the computer 1102 can includea modem 1158, or is connected to a communications server on the WAN1154, or has other means for establishing communications over the WAN1154, such as by way of the Internet. The modem 1158, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1108 via the serial port interface 1142. In a networkedenvironment, program modules depicted relative to the computer 1102, orportions thereof, can be stored in the remote memory/storage device1150. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11x (a,b, g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).

Wi-Fi networks can operate in the unlicensed 2.4 and 5 GHz radio bands.IEEE 802.11 applies to generally to wireless LANs and provides 1 or 2Mbps transmission in the 2.4 GHz band using either frequency hoppingspread spectrum (FHSS) or direct sequence spread spectrum (DSSS). IEEE802.11a is an extension to IEEE 802.11 that applies to wireless LANs andprovides up to 54 Mbps in the 5 GHz band. IEEE 802.11a uses anorthogonal frequency division multiplexing (OFDM) encoding scheme ratherthan FHSS or DSSS. IEEE 802.11b (also referred to as 802.11 High RateDSSS or Wi-Fi) is an extension to 802.11 that applies to wireless LANsand provides 11 Mbps transmission (with a fallback to 5.5, 2 and 1 Mbps)in the 2.4 GHz band. IEEE 802.11g applies to wireless LANs and provides20+ Mbps in the 2.4 GHz band. Products can contain more than one band(e.g., dual band), so the networks can provide real-world performancesimilar to the basic 10BaseT wired Ethernet networks used in manyoffices.

Referring now to FIG. 12, there is illustrated a schematic block diagramof an exemplary computing environment 1200 for processing the disclosedarchitecture in accordance with another aspect. The system 1200 includesone or more client(s) 1202. The client(s) 1202 can be hardware and/orsoftware (e.g., threads, processes, computing devices). The client(s)1202 can house cookie(s) and/or associated contextual information byemploying the claimed subject matter, for example.

The system 1200 also includes one or more server(s) 1204. The server(s)1204 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1204 can house threads to performtransformations by employing the claimed subject matter, for example.One possible communication between a client 1202 and a server 1204 canbe in the form of a data packet adapted to be transmitted between two ormore computer processes. The data packet may include a cookie and/orassociated contextual information, for example. The system 1200 includesa communication framework 1206 (e.g., a global communication networksuch as the Internet) that can be employed to facilitate communicationsbetween the client(s) 1202 and the server(s) 1204.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1202 are operatively connectedto one or more client data store(s) 1208 that can be employed to storeinformation local to the client(s) 1202 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1204 areoperatively connected to one or more server data store(s) 1210 that canbe employed to store information local to the servers 1204.

What has been described above includes examples of the disclosed andclaimed subject matter. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the claimed subject matteris intended to embrace all such alterations, modifications andvariations that fall within the spirit and scope of the appended claims.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

What is claimed is:
 1. A device management system, comprising: areceiver configured to acquire an indication of a device joining anetwork, the device configured to communicate with another device usinga line of sight wireless technology, the device having an antenna, thedevice further configured to communicate with the another device usingthe antenna when within a range of the device; an interface configuredto interrogate the device via the network to obtain currentconfiguration information associated with the device; a managerconfigured to create a device profile for the device based on theobtained configuration information; and memory configured to store thedevice profile for the device.
 2. The device management system of claim1, wherein the obtained configuration information comprisesinterdependent settings.
 3. The device management system of claim 2,wherein the obtained configuration information further comprises atleast one of parameters, network settings or antenna configurationaspects of the device.
 4. The device management system of claim 1,wherein the manager is further configured to employ the indication as atime-sequence event to establish a check point.
 5. The device managementsystem of claim 4, wherein the manager is further configured to utilizethe check point to create a version instance in a version trail, theversion instance being configured to provide an aggregation of changesoccurring between a previous check point and the check point.
 6. Thedevice management system of claim 1, wherein the receiver is furtherconfigured to employ an indication of the device leaving the network asa time-sequence event to establish a check point.
 7. The devicemanagement system of claim 6, wherein the manager is further configuredto utilize the check point to create a version instance in a versiontrail, the version instance being configured to provide an aggregationof changes occurring between a previous check point and the check point.8. The device management system of claim 1, wherein the obtainedconfiguration information comprises at least one antenna configurationassociated with the device.
 9. The device management system of claim 1,wherein the device is further configured to communicate with the anotherdevice using a Wi-Fi network.
 10. The device management system of claim1, wherein the device is further configured to communicate with theanother device using Bluetooth wireless technology.
 11. A devicemanagement system, comprising: a receiver configured to acquire anindication of a device joining a network, the device having an antenna,the device configured to communicate with another device using a line ofsight wireless technology, the device further configured to communicatewith the another device using the antenna when within a range of thedevice a memory configured to store a device profile comprisingconfiguration information for the device; a manager configured to obtainthe device profile comprising configuration information from the memory;and an interface configured to provide the obtained configurationinformation to the device.
 12. The device management system of claim 12,wherein the obtained configuration information comprises at least oneantenna configuration associated with the device.
 13. The devicemanagement system of claim 12, wherein the device is further configuredto communicate with the another device using a Wi-Fi network.
 14. Thedevice management system of claim 12, wherein the device is furtherconfigured to communicate with the another device using Bluetoothwireless technology.
 15. A device management system, comprising: memoryconfigured to store a device profile comprising configurationinformation associated with a device, the device having an antenna, thedevice configured to communicate with another device using a line ofsight wireless technology, the device further configured to communicatewith the another device using the antenna when within a range of thedevice; a receiver configured to acquire an indication of the devicejoining a network; an interface configured to, based at least in part onthe indication, interrogate the device to obtain current configurationsettings of the device; and a manager configured to create anotherdevice profile for the device based on the obtained configurationsettings of the device; wherein the memory is further configured tostore the another device profile for the device as a second version. 16.The device management system of claim 15, wherein the manager is furtherconfigured to generate differences between the device profile and theanother device profile associated with the device.
 17. The devicemanagement system of claim 15, wherein the obtained configurationinformation comprises interdependent settings.
 18. The device managementsystem of claim 15, wherein the device is further configured tocommunicate with the another device using a Wi-Fi network.
 19. Thedevice management system of claim 15, wherein the device is furtherconfigured to communicate with the another device using Bluetoothwireless technology.
 20. The device management system of claim 15,wherein the manager is further configured to employ the indication as atime-sequence event to establish a check point.